Skip to content

added audit check and fix for assets in pending or quarantined state - #323

Merged
shafeeqd959 merged 1 commit into
DX-9302from
DX-10043
Aug 4, 2026
Merged

added audit check and fix for assets in pending or quarantined state#323
shafeeqd959 merged 1 commit into
DX-9302from
DX-10043

Conversation

@shafeeqd959

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 1 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 1 90 / 365 days ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 0
  • Medium without fixes: 1
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

@shafeeqd959
shafeeqd959 changed the base branch from feat/Asset-Scanning-v1 to DX-9302 August 4, 2026 06:53
@shafeeqd959
shafeeqd959 marked this pull request as ready for review August 4, 2026 06:53
@shafeeqd959
shafeeqd959 requested a review from a team as a code owner August 4, 2026 06:53
@shafeeqd959
shafeeqd959 merged commit 5789088 into DX-9302 Aug 4, 2026
9 checks passed
@shafeeqd959
shafeeqd959 deleted the DX-10043 branch August 4, 2026 06:55
netrajpatel added a commit that referenced this pull request Aug 5, 2026
Brings in the 27 commits development gained after the previous merge
(PR #217 Asset-Scanning-v1, #322, #323 and others), clearing the conflict
that was blocking PR #243 and preventing GitHub Actions from producing a
merge ref.

Only .talismanrc conflicted. Resolved to the checksum for the merged
pnpm-lock.yaml (95ad8483..., confirmed via `talisman --checksum`) and moved
`version` back to the top level, where talisman expects it — development's
side had it indented under the fileignoreconfig entry.

Verified before push:
  - `pnpm install --frozen-lockfile` passes (the auto-merged lockfile is
    self-consistent; this is the check that caught the broken lockfile in
    PR #324 and the dropped `open` dependency in the previous merge)
  - dependency sweep against both merge parents: nothing lost
  - undeclared-import sweep unchanged from baseline: no new hybrids
  - test suites for all six packages this merge touched:
      contentstack-audit             160 passing
      contentstack-export            485 passing
      contentstack-external-migrate   42 passing
      contentstack-import           1736 passing
      contentstack-query-export      139 passing
      contentstack-bulk-publish      (no test script)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants